Use two tables (all in UTF8, if you're sure your front-end handles this), the first holding the general product information like code and price, and then the other one holding a record for each language, with the code (as a relation to the other table with general information), the language, and the description in that language.
At 10:48 AM +0800 5/10/03, Terence Ng wrote:
Hi!
I would like to store the title and description of a
product in different languages. Should I use unicode
(UTF-8) to store the different languages in one
database, or I should initialize different databases
for the different languages? I appreciate if someone
can give me some suggestions and what I should aware
of. I have use the keyword "multilingual" to search
the achrieves but cannot find an answer.
Terence
_________________________________________________________
ëÊìÒê¢(é"˪ñN)ÅCèKäµé½ú(óeëcôZ)ÅCåZñÖ(í¬öÛêv)...
Yahoo! óÈþâç
http://ringtone.yahoo.com.hk
---------------------------(end of broadcast)---------------------------
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faqs/FAQ.html
